Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: feacab9834c5b0d966a01b4c60cdbf7d6b3cf8c3352e2978ec380d3460b661c3

Tx prefix hash: 5177a5505f7ac695b17d5dae4aa61bd8376419c7d9c4b1a8751881d55f0d37b4
Tx public key: 53dcf2c01c7342d2af31e305d2907cb4841a53ec090a51394ba51671186d9729
Timestamp: 1698329041 Timestamp [UCT]: 2023-10-26 14:04:01 Age [y:d:h:m:s]: 01:087:11:23:04
Block: 878115 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 323693 RingCT/type: yes/0
Extra: 0153dcf2c01c7342d2af31e305d2907cb4841a53ec090a51394ba51671186d9729021100000004e6d27f9c000000000000000000

1 output(s) for total of 0.755858494000 dcy

stealth address amount amount idx
00: 360dc4b8fff930ad7aff920fb9f05a0b7387a523207c237160bf88d057e45c14 0.755858494000 1333529 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": 878125, "vin": [ { "gen": { "height": 878115 } } ], "vout": [ { "amount": 755858494, "target": { "key": "360dc4b8fff930ad7aff920fb9f05a0b7387a523207c237160bf88d057e45c14" } } ], "extra": [ 1, 83, 220, 242, 192, 28, 115, 66, 210, 175, 49, 227, 5, 210, 144, 124, 180, 132, 26, 83, 236, 9, 10, 81, 57, 75, 165, 22, 113, 24, 109, 151, 41, 2, 17, 0, 0, 0, 4, 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