Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 146d2be8b2d8e21674cccd5108b3cd358ded40a16062efb4d1e307c8c8c99023

Tx prefix hash: 7aa458cb891b81a6f94e86b62fe3f18813a809a91cc953774b5a9fb7f755bd8f
Tx public key: 6899a7c4fbf33ff6bc097afa2d96bb9b4fbaa06bc83f117da78d4f10f0e5361d
Timestamp: 1646720253 Timestamp [UCT]: 2022-03-08 06:17:33 Age [y:d:h:m:s]: 02:290:19:39:32
Block: 453785 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 727369 RingCT/type: yes/0
Extra: 016899a7c4fbf33ff6bc097afa2d96bb9b4fbaa06bc83f117da78d4f10f0e5361d021100000007bf7ee4e7000000000000000000

1 output(s) for total of 19.249621438000 dcy

stealth address amount amount idx
00: 67d2c696a80b6be593bd177705077eee95d4b3aa310e475c0b5a52338589e0d8 19.249621438000 869310 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": 453795, "vin": [ { "gen": { "height": 453785 } } ], "vout": [ { "amount": 19249621438, "target": { "key": "67d2c696a80b6be593bd177705077eee95d4b3aa310e475c0b5a52338589e0d8" } } ], "extra": [ 1, 104, 153, 167, 196, 251, 243, 63, 246, 188, 9, 122, 250, 45, 150, 187, 155, 79, 186, 160, 107, 200, 63, 17, 125, 167, 141, 79, 16, 240, 229, 54, 29, 2, 17, 0, 0, 0, 7, 191, 126, 228, 231, 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