Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 09b0464ff4653df40b6df6a685b0e16d2481392c091519d262a3a0d004c6d601

Tx prefix hash: 64b2bacab06fb1a5e6fe9008a969575f9b231ea48aa8047499ca6e26703a5bf0
Tx public key: b6723f2726b8de11e286a8cd2d7a314da8a74ec2694a06eb84d6f4785373772d
Timestamp: 1720287064 Timestamp [UCT]: 2024-07-06 17:31:04 Age [y:d:h:m:s]: 00:231:20:19:31
Block: 1059934 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 165601 RingCT/type: yes/0
Extra: 01b6723f2726b8de11e286a8cd2d7a314da8a74ec2694a06eb84d6f4785373772d02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f56cb32e71ef1a83946e38130bb8140cb4fce1230bd1cc8956bd991ff255f582 0.600000000000 1530405 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": 1059944, "vin": [ { "gen": { "height": 1059934 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f56cb32e71ef1a83946e38130bb8140cb4fce1230bd1cc8956bd991ff255f582" } } ], "extra": [ 1, 182, 114, 63, 39, 38, 184, 222, 17, 226, 134, 168, 205, 45, 122, 49, 77, 168, 167, 78, 194, 105, 74, 6, 235, 132, 214, 244, 120, 83, 115, 119, 45, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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