Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 71caf40b775e24c37809d4b14a38c2d27eb445507070c0d0537e06127546ccfb

Tx prefix hash: 41226748ca5f19cab39ba408335d4494593a7c071e2b0a9320f9dfef9adbbcb4
Tx public key: b581a1b244b4a2229d25ea560d518d72398d52121402b0c6ee1ca1257edba276
Timestamp: 1765975263 Timestamp [UCT]: 2025-12-17 12:41:03 Age [y:d:h:m:s]: 00:004:06:27:22
Block: 1435570 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 3060 RingCT/type: yes/0
Extra: 01b581a1b244b4a2229d25ea560d518d72398d52121402b0c6ee1ca1257edba276021100000001d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e66a227b0606224e10179308055fcc3c09b0d93912efa8d183a37a876b54b71b 0.600000000000 1924367 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": 1435580, "vin": [ { "gen": { "height": 1435570 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e66a227b0606224e10179308055fcc3c09b0d93912efa8d183a37a876b54b71b" } } ], "extra": [ 1, 181, 129, 161, 178, 68, 180, 162, 34, 157, 37, 234, 86, 13, 81, 141, 114, 57, 141, 82, 18, 20, 2, 176, 198, 238, 28, 161, 37, 126, 219, 162, 118, 2, 17, 0, 0, 0, 1, 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