Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cbc2301626b3506ea638c48356a28843b2a9c20fe36426ca19db95d329d058a8

Tx prefix hash: 6deef79ec1c50188f8db9519218ae6f976a6d69b8966f7a4618d39a7f31b440b
Tx public key: 1decf1365026e65d5ee12da7aaa3a777141bafd717d755c3bb089e4120d7d016
Timestamp: 1725233593 Timestamp [UCT]: 2024-09-01 23:33:13 Age [y:d:h:m:s]: 00:235:19:57:17
Block: 1100951 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 168411 RingCT/type: yes/0
Extra: 011decf1365026e65d5ee12da7aaa3a777141bafd717d755c3bb089e4120d7d016021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8f427e29de9a50fd088856299c58be3d74fd2cb51b1f95904d505a76fcabf6f0 0.600000000000 1576932 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": 1100961, "vin": [ { "gen": { "height": 1100951 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8f427e29de9a50fd088856299c58be3d74fd2cb51b1f95904d505a76fcabf6f0" } } ], "extra": [ 1, 29, 236, 241, 54, 80, 38, 230, 93, 94, 225, 45, 167, 170, 163, 167, 119, 20, 27, 175, 215, 23, 215, 85, 195, 187, 8, 158, 65, 32, 215, 208, 22, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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