Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9ca010a6058d57cf4af6a0a61fef3ef841ba3eb405cea8f92f034121f170c3d8

Tx prefix hash: 8486386095a8b9da228a3a336a97554b7991700ea1d04bb91ca039a6f71c0098
Tx public key: a2f13537b580f894e4fd827e99458a3700edf977e9fd69e31fbf2dd661f002bb
Timestamp: 1736561710 Timestamp [UCT]: 2025-01-11 02:15:10 Age [y:d:h:m:s]: 00:102:05:34:48
Block: 1194711 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72860 RingCT/type: yes/0
Extra: 01a2f13537b580f894e4fd827e99458a3700edf977e9fd69e31fbf2dd661f002bb021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 01f64da266deb735f3f330ae998929e137cf75fa428fb4e33fb343d0e0a991d7 0.600000000000 1681288 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": 1194721, "vin": [ { "gen": { "height": 1194711 } } ], "vout": [ { "amount": 600000000, "target": { "key": "01f64da266deb735f3f330ae998929e137cf75fa428fb4e33fb343d0e0a991d7" } } ], "extra": [ 1, 162, 241, 53, 55, 181, 128, 248, 148, 228, 253, 130, 126, 153, 69, 138, 55, 0, 237, 249, 119, 233, 253, 105, 227, 31, 191, 45, 214, 97, 240, 2, 187, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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