Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8e818cfe99cec825f0c5b60c67337d5f88efe03cbf03255df237b4b8c1f72e0f

Tx prefix hash: 9f9bf905815c767e6546271d979d8cc6c080e889e366649a26e7df6b2b346434
Tx public key: 26b32fc3e880018b66c39d59aaab5e4daaa2902739755c4237718acf8a1fcb7f
Timestamp: 1763228363 Timestamp [UCT]: 2025-11-15 17:39:23 Age [y:d:h:m:s]: 00:037:10:22:01
Block: 1412808 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 26802 RingCT/type: yes/0
Extra: 0126b32fc3e880018b66c39d59aaab5e4daaa2902739755c4237718acf8a1fcb7f021100000004d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2413d0b5993a5997516188ca1530303842fd048e1e43646d042204b2b96e0220 0.600000000000 1901281 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": 1412818, "vin": [ { "gen": { "height": 1412808 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2413d0b5993a5997516188ca1530303842fd048e1e43646d042204b2b96e0220" } } ], "extra": [ 1, 38, 179, 47, 195, 232, 128, 1, 139, 102, 195, 157, 89, 170, 171, 94, 77, 170, 162, 144, 39, 57, 117, 92, 66, 55, 113, 138, 207, 138, 31, 203, 127, 2, 17, 0, 0, 0, 4, 214, 225, 157, 124, 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