Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0879e5a0122f359af3fb3b0ae7de87fd200cbc44cb406a096f60886e1dddf8c5

Tx prefix hash: c6106f5c6c726a1ed32168332033cdb7e53329c83c442bf0997439c15303ee27
Tx public key: c1edaab07c26e20374f74c0c736927e1f589d2a1db02c44e186c5a7ea6a35e31
Timestamp: 1765741463 Timestamp [UCT]: 2025-12-14 19:44:23 Age [y:d:h:m:s]: 00:007:15:01:01
Block: 1433634 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 5463 RingCT/type: yes/0
Extra: 01c1edaab07c26e20374f74c0c736927e1f589d2a1db02c44e186c5a7ea6a35e310211000000017b1e51ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6e03b99a786adbf12da7cc9b3865a2a35c951707a0ae1e89d1174885facecfeb 0.600000000000 1922415 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": 1433644, "vin": [ { "gen": { "height": 1433634 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6e03b99a786adbf12da7cc9b3865a2a35c951707a0ae1e89d1174885facecfeb" } } ], "extra": [ 1, 193, 237, 170, 176, 124, 38, 226, 3, 116, 247, 76, 12, 115, 105, 39, 225, 245, 137, 210, 161, 219, 2, 196, 78, 24, 108, 90, 126, 166, 163, 94, 49, 2, 17, 0, 0, 0, 1, 123, 30, 81, 172, 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