Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3e77ab5ef4ed6afcbddb42688751794108576ad0f6a6f55b860fbee6d3668589

Tx prefix hash: 1a9d65a9fff160aec28457ac90113571fd13e387ef2e6ce79e5ee248f51f3bfe
Tx public key: 0cd8dbc9b4362bf5634317ff2f493613f83a4b9562d55e7fd4d415251f9b26c3
Timestamp: 1761749636 Timestamp [UCT]: 2025-10-29 14:53:56 Age [y:d:h:m:s]: 00:029:00:51:05
Block: 1400571 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 20784 RingCT/type: yes/0
Extra: 010cd8dbc9b4362bf5634317ff2f493613f83a4b9562d55e7fd4d415251f9b26c302110000000525a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 25ad7b121f0b30117c7c77867dc50d383f0a33ba9880d324cc1e8bf0aa055639 0.600000000000 1888888 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": 1400581, "vin": [ { "gen": { "height": 1400571 } } ], "vout": [ { "amount": 600000000, "target": { "key": "25ad7b121f0b30117c7c77867dc50d383f0a33ba9880d324cc1e8bf0aa055639" } } ], "extra": [ 1, 12, 216, 219, 201, 180, 54, 43, 245, 99, 67, 23, 255, 47, 73, 54, 19, 248, 58, 75, 149, 98, 213, 94, 127, 212, 212, 21, 37, 31, 155, 38, 195, 2, 17, 0, 0, 0, 5, 37, 163, 90, 15, 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