Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c7f92603e6662fc3fe48af06510eb4215485561dff3dac64c936fe04ff7c2a0c

Tx prefix hash: 7a91d5ec96cf348451f7ff4185fcb31efc7877295bc9112b24088250b43983a7
Tx public key: 0271d914fddb8d9ddbc4844b0de69d40e1d0cf5c44b81ada350a422f5a4e60d6
Timestamp: 1703643390 Timestamp [UCT]: 2023-12-27 02:16:30 Age [y:d:h:m:s]: 01:113:13:56:46
Block: 921948 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 342304 RingCT/type: yes/0
Extra: 010271d914fddb8d9ddbc4844b0de69d40e1d0cf5c44b81ada350a422f5a4e60d60211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3cec86187ecffe924a46557f7dbab1ed6dd0dd4181d9a5be19bafdfd85b759ac 0.600000000000 1379642 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": 921958, "vin": [ { "gen": { "height": 921948 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3cec86187ecffe924a46557f7dbab1ed6dd0dd4181d9a5be19bafdfd85b759ac" } } ], "extra": [ 1, 2, 113, 217, 20, 253, 219, 141, 157, 219, 196, 132, 75, 13, 230, 157, 64, 225, 208, 207, 92, 68, 184, 26, 218, 53, 10, 66, 47, 90, 78, 96, 214, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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