Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 859873e05b99cee79f591eb9eca1d7ffb60f786f6680519157b4b26d4daf2659

Tx prefix hash: 6f9b8fca0e99c0d37ed684700b5e2b9adc8366cb3219837211e73e1aa179bda1
Tx public key: 8fb898b3c8ef9e8242b63957b5c6c483fc56aa38a194485c37211c46ca78ced0
Timestamp: 1712544594 Timestamp [UCT]: 2024-04-08 02:49:54 Age [y:d:h:m:s]: 00:364:16:22:56
Block: 995715 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 260745 RingCT/type: yes/0
Extra: 018fb898b3c8ef9e8242b63957b5c6c483fc56aa38a194485c37211c46ca78ced00211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9b7b70486aae4e8e4f00ffc569e9f8b71e9667db363cd7eb2dc31e3be6007c6b 0.600000000000 1456129 of 15

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": 995725, "vin": [ { "gen": { "height": 995715 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9b7b70486aae4e8e4f00ffc569e9f8b71e9667db363cd7eb2dc31e3be6007c6b" } } ], "extra": [ 1, 143, 184, 152, 179, 200, 239, 158, 130, 66, 182, 57, 87, 181, 198, 196, 131, 252, 86, 170, 56, 161, 148, 72, 92, 55, 33, 28, 70, 202, 120, 206, 208, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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