Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8105ad3d4bab3c903f897e483472a6515fa573b870527f4da525cf0ab8b7727e

Tx prefix hash: ee492345cb52bfee16ca1be3c6e69308616458c79435a21d7d11138d5e463b15
Tx public key: 20d5ee0377fbf59a8a62e94fb8e89bbb6f53ad6cd01f19e701b2ad839968bbe4
Timestamp: 1624124119 Timestamp [UCT]: 2021-06-19 17:35:19 Age [y:d:h:m:s]: 03:193:21:46:54
Block: 280486 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 905315 RingCT/type: yes/0
Extra: 0120d5ee0377fbf59a8a62e94fb8e89bbb6f53ad6cd01f19e701b2ad839968bbe4021100000027a62ffc6f000000000000000000

1 output(s) for total of 72.217339118000 dcy

stealth address amount amount idx
00: 66644b877b063de4eae2b9106ef170892f25a76942d59baa6d31173c72e7d108 72.217339118000 587367 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": 280496, "vin": [ { "gen": { "height": 280486 } } ], "vout": [ { "amount": 72217339118, "target": { "key": "66644b877b063de4eae2b9106ef170892f25a76942d59baa6d31173c72e7d108" } } ], "extra": [ 1, 32, 213, 238, 3, 119, 251, 245, 154, 138, 98, 233, 79, 184, 232, 155, 187, 111, 83, 173, 108, 208, 31, 25, 231, 1, 178, 173, 131, 153, 104, 187, 228, 2, 17, 0, 0, 0, 39, 166, 47, 252, 111, 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