Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 11aa9047f19a636dd7a7a5ee387f193c3d1e587ed81c023d9ad7cbba99b01fa3

Tx prefix hash: a55e634ce52d7cf20736997c67b6ad1922c396df04916047e9beb22a0e3aa99b
Tx public key: 9c1658e8325212566182e265c39b4f8552de2eb44f1b6a8eb6c19e8933800201
Timestamp: 1648254506 Timestamp [UCT]: 2022-03-26 00:28:26 Age [y:d:h:m:s]: 03:220:18:13:59
Block: 466444 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 935671 RingCT/type: yes/0
Extra: 019c1658e8325212566182e265c39b4f8552de2eb44f1b6a8eb6c19e893380020102110000000706faf294000000000000000000

1 output(s) for total of 17.477433267000 dcy

stealth address amount amount idx
00: 521270b37d78cf1b4cdae210fe5cfaf487cb2a1f0343c738e9b4a7852bba5f15 17.477433267000 884757 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": 466454, "vin": [ { "gen": { "height": 466444 } } ], "vout": [ { "amount": 17477433267, "target": { "key": "521270b37d78cf1b4cdae210fe5cfaf487cb2a1f0343c738e9b4a7852bba5f15" } } ], "extra": [ 1, 156, 22, 88, 232, 50, 82, 18, 86, 97, 130, 226, 101, 195, 155, 79, 133, 82, 222, 46, 180, 79, 27, 106, 142, 182, 193, 158, 137, 51, 128, 2, 1, 2, 17, 0, 0, 0, 7, 6, 250, 242, 148, 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