Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9e5ab23ced44d88627de4d9886f8f805e54dbe17f83d8d9b46a0f773a459f3be

Tx prefix hash: 1708acb5baf03fa1b444f4438f1649073ad1c9c94e4e47039a185368df0ea8a8
Tx public key: ba55eec4f5c9378c1d1f8a7cb5766f82d3e9c8c35d1019ea0df38dd97e620d01
Timestamp: 1675465755 Timestamp [UCT]: 2023-02-03 23:09:15 Age [y:d:h:m:s]: 02:025:20:09:45
Block: 689225 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 540058 RingCT/type: yes/0
Extra: 01ba55eec4f5c9378c1d1f8a7cb5766f82d3e9c8c35d1019ea0df38dd97e620d010211000000075029cbac000000000000000000

1 output(s) for total of 3.193827038000 dcy

stealth address amount amount idx
00: 3e11ae131b739e7222871b8dca546845e60da048ec3a69ef2e1b1011574331dc 3.193827038000 1131889 of 0

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": 689235, "vin": [ { "gen": { "height": 689225 } } ], "vout": [ { "amount": 3193827038, "target": { "key": "3e11ae131b739e7222871b8dca546845e60da048ec3a69ef2e1b1011574331dc" } } ], "extra": [ 1, 186, 85, 238, 196, 245, 201, 55, 140, 29, 31, 138, 124, 181, 118, 111, 130, 211, 233, 200, 195, 93, 16, 25, 234, 13, 243, 141, 217, 126, 98, 13, 1, 2, 17, 0, 0, 0, 7, 80, 41, 203, 172, 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