Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eb5e951466150de40832ae87ff304a14207dc86aaa722c47ad31563af42577e0

Tx prefix hash: aa338f7235dc8d8f1efbdaf77b0624eac1266851440d1c330c9a17e4fb25953d
Tx public key: 6722731f9228e0f3d60de3fdfebe6fb3463645089e0158054293efca7c559832
Timestamp: 1652277830 Timestamp [UCT]: 2022-05-11 14:03:50 Age [y:d:h:m:s]: 03:012:10:55:50
Block: 498760 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 790090 RingCT/type: yes/0
Extra: 016722731f9228e0f3d60de3fdfebe6fb3463645089e0158054293efca7c55983202110000001a2e6b1fd5000000000000000000

1 output(s) for total of 13.658445756000 dcy

stealth address amount amount idx
00: 9386af25f557972efab21bb4a8f6e9c59e844d2d1d36666e4d0b1a8e274ccfa9 13.658445756000 922999 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": 498770, "vin": [ { "gen": { "height": 498760 } } ], "vout": [ { "amount": 13658445756, "target": { "key": "9386af25f557972efab21bb4a8f6e9c59e844d2d1d36666e4d0b1a8e274ccfa9" } } ], "extra": [ 1, 103, 34, 115, 31, 146, 40, 224, 243, 214, 13, 227, 253, 254, 190, 111, 179, 70, 54, 69, 8, 158, 1, 88, 5, 66, 147, 239, 202, 124, 85, 152, 50, 2, 17, 0, 0, 0, 26, 46, 107, 31, 213, 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