Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 18c28bad4eb665a0670e1cc47c110f9f7274cc0055c87b449d3dd0f900d00287

Tx prefix hash: 9a385e9a01a7516c5e2caffce07ef4d5038b3a3eb67ce8dd78bb1264d8d17d2e
Tx public key: a3de8bb67c4487f31e6c8ad351378eb9aebec9f560a9509c0ff8d27408349b62
Timestamp: 1706666418 Timestamp [UCT]: 2024-01-31 02:00:18 Age [y:d:h:m:s]: 01:077:00:54:18
Block: 946991 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 316138 RingCT/type: yes/0
Extra: 01a3de8bb67c4487f31e6c8ad351378eb9aebec9f560a9509c0ff8d27408349b620211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5f6c9b336d827ac2347fb7fa9c3254a96e2a4b1a15b899c78fc46e0ae3b8e3b2 0.600000000000 1405337 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": 947001, "vin": [ { "gen": { "height": 946991 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5f6c9b336d827ac2347fb7fa9c3254a96e2a4b1a15b899c78fc46e0ae3b8e3b2" } } ], "extra": [ 1, 163, 222, 139, 182, 124, 68, 135, 243, 30, 108, 138, 211, 81, 55, 142, 185, 174, 190, 201, 245, 96, 169, 80, 156, 15, 248, 210, 116, 8, 52, 155, 98, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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