Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b2aa947a816559b7531b72e4361ca0546bcc3cbe7cdeafc9fc0460a400780642

Tx prefix hash: e1e790f5bf39411d2ea1a1ca90fa5f199fce28b0a14acea2225ed929257419a5
Tx public key: 4a5e7de14d709c3f4a8ad091de039ac1c65df78a7ef87ea9df5213e6d0b52a14
Timestamp: 1702204517 Timestamp [UCT]: 2023-12-10 10:35:17 Age [y:d:h:m:s]: 00:354:08:54:34
Block: 910026 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 253734 RingCT/type: yes/0
Extra: 014a5e7de14d709c3f4a8ad091de039ac1c65df78a7ef87ea9df5213e6d0b52a14021100000005e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b7992f7aa7c33ae25df313b968e8dc438489ec35a2828155bbbc5caf16000ae4 0.600000000000 1367167 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": 910036, "vin": [ { "gen": { "height": 910026 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b7992f7aa7c33ae25df313b968e8dc438489ec35a2828155bbbc5caf16000ae4" } } ], "extra": [ 1, 74, 94, 125, 225, 77, 112, 156, 63, 74, 138, 208, 145, 222, 3, 154, 193, 198, 93, 247, 138, 126, 248, 126, 169, 223, 82, 19, 230, 208, 181, 42, 20, 2, 17, 0, 0, 0, 5, 230, 210, 127, 156, 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