Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4511b44d5a4eb1c7b24afeab654b9d2f8ca5bf3728d64b3c8a5c12f21417e197

Tx prefix hash: c59f6864e671f5b081f8ac4ddb0efce311ec4c9a875408f43a5f703a81716bbd
Tx public key: cfd6416ef2dfa9f83dd38cc19475b8f30344adca25ee98733a951be55fb3a91b
Timestamp: 1697335809 Timestamp [UCT]: 2023-10-15 02:10:09 Age [y:d:h:m:s]: 01:212:12:20:34
Block: 869859 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 412952 RingCT/type: yes/0
Extra: 01cfd6416ef2dfa9f83dd38cc19475b8f30344adca25ee98733a951be55fb3a91b02110000000375e3f0e9000000000000000000

1 output(s) for total of 0.805000342000 dcy

stealth address amount amount idx
00: 220a6f06c62805da7271f795f207a41d519f9a4a5c2ed0e1f350a1d4d96376d9 0.805000342000 1324722 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": 869869, "vin": [ { "gen": { "height": 869859 } } ], "vout": [ { "amount": 805000342, "target": { "key": "220a6f06c62805da7271f795f207a41d519f9a4a5c2ed0e1f350a1d4d96376d9" } } ], "extra": [ 1, 207, 214, 65, 110, 242, 223, 169, 248, 61, 211, 140, 193, 148, 117, 184, 243, 3, 68, 173, 202, 37, 238, 152, 115, 58, 149, 27, 229, 95, 179, 169, 27, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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