Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 558f329eb4c69ee24a7ffa90ab46f48461b58e8bdac3c83e9d7611b4ee54fe81

Tx prefix hash: 17765725da94ec898f559db00887886c25bfb9ec5f2062e44cc6ad1bbcceba90
Tx public key: 3d1ae8f03d8ef67d2054f2f5cfe6fc0b32b16bd43784b42954238f1070ed6c61
Timestamp: 1706706660 Timestamp [UCT]: 2024-01-31 13:11:00 Age [y:d:h:m:s]: 01:072:03:29:42
Block: 947333 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 312637 RingCT/type: yes/0
Extra: 013d1ae8f03d8ef67d2054f2f5cfe6fc0b32b16bd43784b42954238f1070ed6c6102110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8f49b5cf836aaf9be72c4a6ee9cac1f5c074c1d9e02f872d65a4c2237f2b0683 0.600000000000 1405681 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": 947343, "vin": [ { "gen": { "height": 947333 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8f49b5cf836aaf9be72c4a6ee9cac1f5c074c1d9e02f872d65a4c2237f2b0683" } } ], "extra": [ 1, 61, 26, 232, 240, 61, 142, 246, 125, 32, 84, 242, 245, 207, 230, 252, 11, 50, 177, 107, 212, 55, 132, 180, 41, 84, 35, 143, 16, 112, 237, 108, 97, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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