Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 339e2bd7e56ed80fb83f8bc67d362f131c2910de4be96f2ab7c301bd63537aa0

Tx prefix hash: c3747b8e71db2ac262354a322375ea4ed10546ae7233de980f9d40dca39d890b
Tx public key: 79cfc8ebbc0dca50b89d47358cda9fe5f23cf1f417e9eb5948812fe862d60b53
Timestamp: 1701836307 Timestamp [UCT]: 2023-12-06 04:18:27 Age [y:d:h:m:s]: 01:161:02:03:36
Block: 906962 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 376314 RingCT/type: yes/0
Extra: 0179cfc8ebbc0dca50b89d47358cda9fe5f23cf1f417e9eb5948812fe862d60b53021100000005faf35c9c000000000000000000

1 output(s) for total of 0.606538495000 dcy

stealth address amount amount idx
00: 7b465dd72de55a636f019b2d95dc3c86255fcb1f735de2e5fe8fa84881fd32c7 0.606538495000 1363925 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": 906972, "vin": [ { "gen": { "height": 906962 } } ], "vout": [ { "amount": 606538495, "target": { "key": "7b465dd72de55a636f019b2d95dc3c86255fcb1f735de2e5fe8fa84881fd32c7" } } ], "extra": [ 1, 121, 207, 200, 235, 188, 13, 202, 80, 184, 157, 71, 53, 140, 218, 159, 229, 242, 60, 241, 244, 23, 233, 235, 89, 72, 129, 47, 232, 98, 214, 11, 83, 2, 17, 0, 0, 0, 5, 250, 243, 92, 156, 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