Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3240f5d829b8849bb021f2cb50afee367eaf8b5b9fa9aa3504563d2bf8ae261f

Tx prefix hash: 648a5b16309b47565e5ab7996c9f92145912cb4709d4f52a238c46bf81221b2a
Tx public key: c1b141a44f171d14b692752c1f3a109585a076a7f9d6808e7ceed4d5dddd07c3
Timestamp: 1737690938 Timestamp [UCT]: 2025-01-24 03:55:38 Age [y:d:h:m:s]: 00:144:22:25:11
Block: 1204021 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103334 RingCT/type: yes/0
Extra: 01c1b141a44f171d14b692752c1f3a109585a076a7f9d6808e7ceed4d5dddd07c30211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f12a2755dd0f6746b9538f004c7acb747334c2cedc7f947974d6e80d78b1df99 0.600000000000 1690702 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": 1204031, "vin": [ { "gen": { "height": 1204021 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f12a2755dd0f6746b9538f004c7acb747334c2cedc7f947974d6e80d78b1df99" } } ], "extra": [ 1, 193, 177, 65, 164, 79, 23, 29, 20, 182, 146, 117, 44, 31, 58, 16, 149, 133, 160, 118, 167, 249, 214, 128, 142, 124, 238, 212, 213, 221, 221, 7, 195, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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