Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c057f612571725a994ad94d7763519c8a762d445ff1fd7a173009cdfdf81dc0c

Tx prefix hash: 9732f4fe3b40585e0cadcf3e4856ad0142ccd9796ef43bfaca6b1e192bc31a8e
Tx public key: c897ef2a42435a0336fcad908f5646e72a897536f174f2c877bb2c870410bb0f
Timestamp: 1735412889 Timestamp [UCT]: 2024-12-28 19:08:09 Age [y:d:h:m:s]: 00:172:13:49:53
Block: 1185202 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 123041 RingCT/type: yes/0
Extra: 01c897ef2a42435a0336fcad908f5646e72a897536f174f2c877bb2c870410bb0f0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e18a93d5c36244d72b427a43ebb5e0df0f549f29b7c4411f96dd16b17b54c2c6 0.600000000000 1671669 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": 1185212, "vin": [ { "gen": { "height": 1185202 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e18a93d5c36244d72b427a43ebb5e0df0f549f29b7c4411f96dd16b17b54c2c6" } } ], "extra": [ 1, 200, 151, 239, 42, 66, 67, 90, 3, 54, 252, 173, 144, 143, 86, 70, 231, 42, 137, 117, 54, 241, 116, 242, 200, 119, 187, 44, 135, 4, 16, 187, 15, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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