Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eb6a29047f478c7eb6d7ff1805db047d09efbb7db1251f0bf792f2eca818acac

Tx prefix hash: 48c9b096769408aa6456b35574b625a944a07f22a8ecd82444276d0843478165
Tx public key: 919bcbb426a1595177661b7e0d1e4fc87055e8498a7df690289f5dc8adbe7525
Timestamp: 1730677081 Timestamp [UCT]: 2024-11-03 23:38:01 Age [y:d:h:m:s]: 00:150:00:03:45
Block: 1145994 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107023 RingCT/type: yes/0
Extra: 01919bcbb426a1595177661b7e0d1e4fc87055e8498a7df690289f5dc8adbe75250211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a1f0a0b9e6b6bf2807ae4c95d10c05d3b87aea7d8e3c5ef157df766b99c21b94 0.600000000000 1630539 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": 1146004, "vin": [ { "gen": { "height": 1145994 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a1f0a0b9e6b6bf2807ae4c95d10c05d3b87aea7d8e3c5ef157df766b99c21b94" } } ], "extra": [ 1, 145, 155, 203, 180, 38, 161, 89, 81, 119, 102, 27, 126, 13, 30, 79, 200, 112, 85, 232, 73, 138, 125, 246, 144, 40, 159, 93, 200, 173, 190, 117, 37, 2, 17, 0, 0, 0, 3, 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