Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 70469c1c05fb49a80a64dc1088289011ae070de0fd116739688abe764d09294d

Tx prefix hash: 908592b65f9c7d58270a522d9cf02da979b8e9049d477684bb94ab3785e6c2d4
Tx public key: 523a63238b94ab729013aeb7dc28bc101a9b476ece77ad4c0a2e72351c1e64d8
Timestamp: 1695051335 Timestamp [UCT]: 2023-09-18 15:35:35 Age [y:d:h:m:s]: 01:275:04:01:01
Block: 850913 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 457661 RingCT/type: yes/0
Extra: 01523a63238b94ab729013aeb7dc28bc101a9b476ece77ad4c0a2e72351c1e64d802110000000475e3f0e9000000000000000000

1 output(s) for total of 0.930190834000 dcy

stealth address amount amount idx
00: 08b39db70753765e1d74f7e996cce92a3b2fe6f611e9afbbd494e2d13cd501d3 0.930190834000 1304663 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": 850923, "vin": [ { "gen": { "height": 850913 } } ], "vout": [ { "amount": 930190834, "target": { "key": "08b39db70753765e1d74f7e996cce92a3b2fe6f611e9afbbd494e2d13cd501d3" } } ], "extra": [ 1, 82, 58, 99, 35, 139, 148, 171, 114, 144, 19, 174, 183, 220, 40, 188, 16, 26, 155, 71, 110, 206, 119, 173, 76, 10, 46, 114, 53, 28, 30, 100, 216, 2, 17, 0, 0, 0, 4, 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