Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 71592d1eda3b65578eca58b6621c079e87d4cb997d56d7ee7f6258d829a196a9

Tx prefix hash: fb31f9d85e00e195ccbe843bd9a0a09c0b0682e34b5d075d43d55fd4bd20671d
Tx public key: dc28eceac2259173e7455cdbc891bcfd16fe4a3d39ce71d2a744bf28662645b4
Timestamp: 1702452493 Timestamp [UCT]: 2023-12-13 07:28:13 Age [y:d:h:m:s]: 01:180:00:25:39
Block: 912102 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 389808 RingCT/type: yes/0
Extra: 01dc28eceac2259173e7455cdbc891bcfd16fe4a3d39ce71d2a744bf28662645b402110000000233af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f20249d9e8dc412b10b4069f196e11a430a08f586d043c887b1304f8d9f4891f 0.600000000000 1369322 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": 912112, "vin": [ { "gen": { "height": 912102 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f20249d9e8dc412b10b4069f196e11a430a08f586d043c887b1304f8d9f4891f" } } ], "extra": [ 1, 220, 40, 236, 234, 194, 37, 145, 115, 231, 69, 92, 219, 200, 145, 188, 253, 22, 254, 74, 61, 57, 206, 113, 210, 167, 68, 191, 40, 102, 38, 69, 180, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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