Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5c9e6d53f87a53d7a7c137ca897f451aa35975baa3bafd6995faef34c43f585a

Tx prefix hash: e844de8348241830d083b397a038d44f0c287a2c3da528d26b50261bdad7e653
Tx public key: 58377b938d4a07c324cb75908dafc83b41809fb8c5217f88736d5c5406272399
Timestamp: 1763113311 Timestamp [UCT]: 2025-11-14 09:41:51 Age [y:d:h:m:s]: 00:050:12:21:42
Block: 1411864 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 36173 RingCT/type: yes/0
Extra: 0158377b938d4a07c324cb75908dafc83b41809fb8c5217f88736d5c54062723990211000000042609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 392a1d22d27afef904509542e05a89f89a14ce5e98a9fad59718d93e7311ade1 0.600000000000 1900329 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": 1411874, "vin": [ { "gen": { "height": 1411864 } } ], "vout": [ { "amount": 600000000, "target": { "key": "392a1d22d27afef904509542e05a89f89a14ce5e98a9fad59718d93e7311ade1" } } ], "extra": [ 1, 88, 55, 123, 147, 141, 74, 7, 195, 36, 203, 117, 144, 141, 175, 200, 59, 65, 128, 159, 184, 197, 33, 127, 136, 115, 109, 92, 84, 6, 39, 35, 153, 2, 17, 0, 0, 0, 4, 38, 9, 179, 160, 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