Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fd8e0e1eeef938bdbd5e89bc62a98867ce67dc9945616a6885def03cac896b42

Tx prefix hash: 474b5b0ff7e5ffdbeeb908e68f618c00f1f9a64016e8fc88de0527f0936675e8
Tx public key: 84f46e928da38cf7ea34641b0634a558b68d89f8aca83c8fb66ef114c3849f38
Timestamp: 1674074910 Timestamp [UCT]: 2023-01-18 20:48:30 Age [y:d:h:m:s]: 02:041:15:24:06
Block: 677673 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 551394 RingCT/type: yes/0
Extra: 0184f46e928da38cf7ea34641b0634a558b68d89f8aca83c8fb66ef114c3849f3802110000000152542ceb000000000000000000

1 output(s) for total of 3.488092405000 dcy

stealth address amount amount idx
00: e6d555b938ef43e48dfb6e300ab2fdca7a1865def69cfb4486df9a3b01da591d 3.488092405000 1119462 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": 677683, "vin": [ { "gen": { "height": 677673 } } ], "vout": [ { "amount": 3488092405, "target": { "key": "e6d555b938ef43e48dfb6e300ab2fdca7a1865def69cfb4486df9a3b01da591d" } } ], "extra": [ 1, 132, 244, 110, 146, 141, 163, 140, 247, 234, 52, 100, 27, 6, 52, 165, 88, 182, 141, 137, 248, 172, 168, 60, 143, 182, 110, 241, 20, 195, 132, 159, 56, 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