Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7067b243ef2eed4fcf6157311892d0e172068f4d42a51c4e99e76660cf2c1bc1

Tx prefix hash: b8af266aa735ac29368359290290269ea3eb89d09ac4ef83af0c0f9911b2b82b
Tx public key: 6f705b3ad2d811f27ad4262acfdebc332dbbb0cd565b7e2f577e1c0dc5bde9c4
Timestamp: 1674075928 Timestamp [UCT]: 2023-01-18 21:05:28 Age [y:d:h:m:s]: 01:364:16:30:40
Block: 677685 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 521662 RingCT/type: yes/0
Extra: 016f705b3ad2d811f27ad4262acfdebc332dbbb0cd565b7e2f577e1c0dc5bde9c402110000000152542ceb000000000000000000

1 output(s) for total of 3.487773074000 dcy

stealth address amount amount idx
00: 251c49bf9f04e3127a80d75f2618147dbe735ba1387456726a053e55bb0194f6 3.487773074000 1119474 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": 677695, "vin": [ { "gen": { "height": 677685 } } ], "vout": [ { "amount": 3487773074, "target": { "key": "251c49bf9f04e3127a80d75f2618147dbe735ba1387456726a053e55bb0194f6" } } ], "extra": [ 1, 111, 112, 91, 58, 210, 216, 17, 242, 122, 212, 38, 42, 207, 222, 188, 51, 45, 187, 176, 205, 86, 91, 126, 47, 87, 126, 28, 13, 197, 189, 233, 196, 2, 17, 0, 0, 0, 1, 82, 84, 44, 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