Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 40a0b1dbb222e273898e5cd375bbd98b283a000f9dab65803939a72ef675a3ca

Tx prefix hash: 25812ccc6bce1f1ed15a450d76d48f71f3b22968e82347213b9675a7cab8dc74
Tx public key: a417604aefd688d7cc40075c856c397f9f1bf4033d8011cbf830a4267d4a2e9d
Timestamp: 1682253947 Timestamp [UCT]: 2023-04-23 12:45:47 Age [y:d:h:m:s]: 01:274:11:10:20
Block: 744869 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 457609 RingCT/type: yes/0
Extra: 01a417604aefd688d7cc40075c856c397f9f1bf4033d8011cbf830a4267d4a2e9d021100000004b3164c24000000000000000000

1 output(s) for total of 2.089007522000 dcy

stealth address amount amount idx
00: 22d5e25363982954004e92fbfa3197bcd8873cd33274ea764c6a7f3514ef3f0c 2.089007522000 1192260 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": 744879, "vin": [ { "gen": { "height": 744869 } } ], "vout": [ { "amount": 2089007522, "target": { "key": "22d5e25363982954004e92fbfa3197bcd8873cd33274ea764c6a7f3514ef3f0c" } } ], "extra": [ 1, 164, 23, 96, 74, 239, 214, 136, 215, 204, 64, 7, 92, 133, 108, 57, 127, 159, 27, 244, 3, 61, 128, 17, 203, 248, 48, 164, 38, 125, 74, 46, 157, 2, 17, 0, 0, 0, 4, 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