Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d03edea327506386c660ec61774ecc1b61b2cda3e4225593f31b72997ecf04ad

Tx prefix hash: 6599b07ff124143f4e6b534519c3d15922332ad5666a5d4013618ff01a14c692
Tx public key: b762291fdaa7c61100a7486b5cb32d0c55bf91e40d135f5f3133890a01c5ec7f
Timestamp: 1684606428 Timestamp [UCT]: 2023-05-20 18:13:48 Age [y:d:h:m:s]: 01:196:23:21:44
Block: 764383 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 402186 RingCT/type: yes/0
Extra: 01b762291fdaa7c61100a7486b5cb32d0c55bf91e40d135f5f3133890a01c5ec7f021100000003faf35c9c000000000000000000

1 output(s) for total of 1.800039323000 dcy

stealth address amount amount idx
00: 7d61563ffafd35a8ada3b0a76262cfae97dc7692f39d10e07f1d9a0cdf6e3440 1.800039323000 1213300 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": 764393, "vin": [ { "gen": { "height": 764383 } } ], "vout": [ { "amount": 1800039323, "target": { "key": "7d61563ffafd35a8ada3b0a76262cfae97dc7692f39d10e07f1d9a0cdf6e3440" } } ], "extra": [ 1, 183, 98, 41, 31, 218, 167, 198, 17, 0, 167, 72, 107, 92, 179, 45, 12, 85, 191, 145, 228, 13, 19, 95, 95, 49, 51, 137, 10, 1, 197, 236, 127, 2, 17, 0, 0, 0, 3, 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