Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4345197f2a34aae2fa53c7aea4c1798411f99890c419b1746b61717ef1f1606e

Tx prefix hash: 61d2435902d45c0004c41eae9fe39ae3b0567e692ad10a29ef0fb544826e8f3a
Tx public key: 21ae04f866078e406d7e3ffb9e3a94240dd29c0d342352a3e7d5a30f984050fe
Timestamp: 1752636292 Timestamp [UCT]: 2025-07-16 03:24:52 Age [y:d:h:m:s]: 00:117:21:18:58
Block: 1326455 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 82991 RingCT/type: yes/0
Extra: 0121ae04f866078e406d7e3ffb9e3a94240dd29c0d342352a3e7d5a30f984050fe02110000000143846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 95d8e4c77fe184a0a71aa1e63854f6a2e65c5d235b3a5a310754a3ef2a51d416 0.600000000000 1814206 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": 1326465, "vin": [ { "gen": { "height": 1326455 } } ], "vout": [ { "amount": 600000000, "target": { "key": "95d8e4c77fe184a0a71aa1e63854f6a2e65c5d235b3a5a310754a3ef2a51d416" } } ], "extra": [ 1, 33, 174, 4, 248, 102, 7, 142, 64, 109, 126, 63, 251, 158, 58, 148, 36, 13, 210, 156, 13, 52, 35, 82, 163, 231, 213, 163, 15, 152, 64, 80, 254, 2, 17, 0, 0, 0, 1, 67, 132, 109, 102, 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