Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ecf7829d3d05277bd91a8fb8978f9832e8bebb8b8b063b620bda5affc3b548ec

Tx prefix hash: 9d89d770161926b12f3c4334526932c914b73c6c265c29117a703e5760fe26c4
Tx public key: b7b2f448326ae5f36b2205a05033b8a4e57832ba0e9925c141fdb3d4962dee18
Timestamp: 1682846488 Timestamp [UCT]: 2023-04-30 09:21:28 Age [y:d:h:m:s]: 01:300:07:50:07
Block: 749788 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 475849 RingCT/type: yes/0
Extra: 01b7b2f448326ae5f36b2205a05033b8a4e57832ba0e9925c141fdb3d4962dee18021100000006b3164c24000000000000000000

1 output(s) for total of 2.012061762000 dcy

stealth address amount amount idx
00: 1226768584d55dd597c9b79b542432f5b9bc5108583a0b150a50383c2f06a381 2.012061762000 1197795 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": 749798, "vin": [ { "gen": { "height": 749788 } } ], "vout": [ { "amount": 2012061762, "target": { "key": "1226768584d55dd597c9b79b542432f5b9bc5108583a0b150a50383c2f06a381" } } ], "extra": [ 1, 183, 178, 244, 72, 50, 106, 229, 243, 107, 34, 5, 160, 80, 51, 184, 164, 229, 120, 50, 186, 14, 153, 37, 193, 65, 253, 179, 212, 150, 45, 238, 24, 2, 17, 0, 0, 0, 6, 179, 22, 76, 36, 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