Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 537c776f5edc7ed34e49b8ba8735483f0bf2196c087482dcfd216e7b88f6b8d9

Tx prefix hash: a889ce27d34645328b2d5f4396091666d80b626f34f5de02f8b9c86ef66258d8
Tx public key: a1a61cd2e9f36418006302547697aefbc07015e554ef33a770b82c0ea79dcdf3
Timestamp: 1698693240 Timestamp [UCT]: 2023-10-30 19:14:00 Age [y:d:h:m:s]: 01:117:22:18:12
Block: 881129 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 345237 RingCT/type: yes/0
Extra: 01a1a61cd2e9f36418006302547697aefbc07015e554ef33a770b82c0ea79dcdf30211000000014b8f5122000000000000000000

1 output(s) for total of 0.738675781000 dcy

stealth address amount amount idx
00: 610c73b5f20957c8e37869ae03af6d5d71c5ba394d993892540714ac3a5bacd6 0.738675781000 1336705 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": 881139, "vin": [ { "gen": { "height": 881129 } } ], "vout": [ { "amount": 738675781, "target": { "key": "610c73b5f20957c8e37869ae03af6d5d71c5ba394d993892540714ac3a5bacd6" } } ], "extra": [ 1, 161, 166, 28, 210, 233, 243, 100, 24, 0, 99, 2, 84, 118, 151, 174, 251, 192, 112, 21, 229, 84, 239, 51, 167, 112, 184, 44, 14, 167, 157, 205, 243, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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