Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: f349c87702cb980ba4b14fff0f24acb115badf8d0728d1c7cce2e9dcfaa873f0

Tx prefix hash: c8621afeb415abc26e2e313afa1673d0c1fff2e16163029eb4cecc038d51f6ea
Tx public key: d7dc8f4ad666bc5226e774e5f4d9c3d7fbfb380d905da0cf202200fb508e9214
Timestamp: 1717074291 Timestamp [UCT]: 2024-05-30 13:04:51 Age [y:d:h:m:s]: 00:310:04:26:50
Block: 1033302 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 221688 RingCT/type: yes/0
Extra: 01d7dc8f4ad666bc5226e774e5f4d9c3d7fbfb380d905da0cf202200fb508e92140211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7fb20ae2dd4f80a5dfbe8621cc8a3eb26e4d9f750abc3e5da4a1dac676238b2f 0.600000000000 1501767 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1033312, "vin": [ { "gen": { "height": 1033302 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7fb20ae2dd4f80a5dfbe8621cc8a3eb26e4d9f750abc3e5da4a1dac676238b2f" } } ], "extra": [ 1, 215, 220, 143, 74, 214, 102, 188, 82, 38, 231, 116, 229, 244, 217, 195, 215, 251, 251, 56, 13, 144, 93, 160, 207, 32, 34, 0, 251, 80, 142, 146, 20, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8