Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fb00f2af05b4bc982870459c18a4a220181000b700f582abd96fe7db91834bc7

Tx prefix hash: 40f4e3fd5af64fa1a898f1a76035617270968f1bfb965cee315c4e796568e499
Tx public key: dd473ed76f079baaedc60674b3ae47e26bdf2b3d7707ebc9500d66fbb8b6489f
Timestamp: 1702678151 Timestamp [UCT]: 2023-12-15 22:09:11 Age [y:d:h:m:s]: 01:336:22:46:38
Block: 913943 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 499683 RingCT/type: yes/0
Extra: 01dd473ed76f079baaedc60674b3ae47e26bdf2b3d7707ebc9500d66fbb8b6489f02110000000275e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a71bcb592126b404dc7d2def4f57b782f1d2239e5348452f4d109e03faaf281a 0.600000000000 1371223 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": 913953, "vin": [ { "gen": { "height": 913943 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a71bcb592126b404dc7d2def4f57b782f1d2239e5348452f4d109e03faaf281a" } } ], "extra": [ 1, 221, 71, 62, 215, 111, 7, 155, 170, 237, 198, 6, 116, 179, 174, 71, 226, 107, 223, 43, 61, 119, 7, 235, 201, 80, 13, 102, 251, 184, 182, 72, 159, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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