Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc61a175aca2b16823324d18c2b510bd77b0356d3a1ebc2f2b781e28321718b6

Tx prefix hash: d37971432203f0d4b47d93ac964aa7c312839005c4d9be67ff8aecd46c993dbd
Tx public key: 7c001c4b2f6beddab89c7c1be28af12bf500f203b347e95c51b37e457e9e8896
Timestamp: 1711012046 Timestamp [UCT]: 2024-03-21 09:07:26 Age [y:d:h:m:s]: 01:034:18:12:03
Block: 983060 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 285814 RingCT/type: yes/0
Extra: 017c001c4b2f6beddab89c7c1be28af12bf500f203b347e95c51b37e457e9e889602110000000a0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4b27d357fa1dc61648dbf356f93416df504d863967bcceda29512aa40e9ecdb3 0.600000000000 1443179 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": 983070, "vin": [ { "gen": { "height": 983060 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4b27d357fa1dc61648dbf356f93416df504d863967bcceda29512aa40e9ecdb3" } } ], "extra": [ 1, 124, 0, 28, 75, 47, 107, 237, 218, 184, 156, 124, 27, 226, 138, 241, 43, 245, 0, 242, 3, 179, 71, 233, 92, 81, 179, 126, 69, 126, 158, 136, 150, 2, 17, 0, 0, 0, 10, 0, 17, 5, 91, 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