Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3b58dc3d79f78f2858fb0a8e2d0008912384c2a0ebdd4008e67af951e3f3a755

Tx prefix hash: c9e7934053f72560c0375d71326d3cd899e394ffcc84087363c5df70ce7bfe8f
Tx public key: fc90704f8f55f229c8710792ab6a2564ed83d03b4a9660015f1215782a48fd3a
Timestamp: 1717531894 Timestamp [UCT]: 2024-06-04 20:11:34 Age [y:d:h:m:s]: 00:218:17:38:57
Block: 1037102 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 156539 RingCT/type: yes/0
Extra: 01fc90704f8f55f229c8710792ab6a2564ed83d03b4a9660015f1215782a48fd3a0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8f62e7c980fbe9a54898f7e8d8145b81869c8d4bf634aa57990eb2d65741b758 0.600000000000 1505633 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": 1037112, "vin": [ { "gen": { "height": 1037102 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8f62e7c980fbe9a54898f7e8d8145b81869c8d4bf634aa57990eb2d65741b758" } } ], "extra": [ 1, 252, 144, 112, 79, 143, 85, 242, 41, 200, 113, 7, 146, 171, 106, 37, 100, 237, 131, 208, 59, 74, 150, 96, 1, 95, 18, 21, 120, 42, 72, 253, 58, 2, 17, 0, 0, 0, 1, 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