Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fc04741cf8bf15b2c38487b6da96a4169fdcb86280d8b592b3b0570d4aca9183

Tx prefix hash: d783f1d80ec2333d6319b8d46767e9acdd6908d07beb90a7effc0d90a8285a18
Tx public key: db01ecedc71c39650579b4b48dec4451022fd2f849e5afaae23725ca2128f97a
Timestamp: 1612518342 Timestamp [UCT]: 2021-02-05 09:45:42 Age [y:d:h:m:s]: 03:326:12:15:10
Block: 192489 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 992082 RingCT/type: yes/0
Extra: 01db01ecedc71c39650579b4b48dec4451022fd2f849e5afaae23725ca2128f97a021100000006b9b01d0b000000000000000000

1 output(s) for total of 141.320339114000 dcy

stealth address amount amount idx
00: 1703e61a51b3a147fbf934a473539b2c282de3f2af953bee1d08ad18a8fe75d1 141.320339114000 388377 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": 192499, "vin": [ { "gen": { "height": 192489 } } ], "vout": [ { "amount": 141320339114, "target": { "key": "1703e61a51b3a147fbf934a473539b2c282de3f2af953bee1d08ad18a8fe75d1" } } ], "extra": [ 1, 219, 1, 236, 237, 199, 28, 57, 101, 5, 121, 180, 180, 141, 236, 68, 81, 2, 47, 210, 248, 73, 229, 175, 170, 226, 55, 37, 202, 33, 40, 249, 122, 2, 17, 0, 0, 0, 6, 185, 176, 29, 11, 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