Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 47a3bc3f0ffb373c187515ec210a7cc93079b8d5cb2ce35249f55115746e9b64

Tx prefix hash: 2bc3bd7d16e029fa33f1b2c4597881c81fa5024938b7f38ae6af8743c5246fa8
Tx public key: 3fd6bc08f1718eb2067416b497d06d527f9633552679d88a4c3768be9b44ce9b
Timestamp: 1685495929 Timestamp [UCT]: 2023-05-31 01:18:49 Age [y:d:h:m:s]: 02:159:23:20:46
Block: 771757 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 634093 RingCT/type: yes/0
Extra: 013fd6bc08f1718eb2067416b497d06d527f9633552679d88a4c3768be9b44ce9b021100000001e6d27f9c000000000000000000

1 output(s) for total of 1.701566234000 dcy

stealth address amount amount idx
00: 16b9ab54b891e0c4300b855bf71db528b0bbd2868577f00e30639039cc651269 1.701566234000 1221134 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": 771767, "vin": [ { "gen": { "height": 771757 } } ], "vout": [ { "amount": 1701566234, "target": { "key": "16b9ab54b891e0c4300b855bf71db528b0bbd2868577f00e30639039cc651269" } } ], "extra": [ 1, 63, 214, 188, 8, 241, 113, 142, 178, 6, 116, 22, 180, 151, 208, 109, 82, 127, 150, 51, 85, 38, 121, 216, 138, 76, 55, 104, 190, 155, 68, 206, 155, 2, 17, 0, 0, 0, 1, 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