Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 794bcd83495af1c22b13220af2f8e51e10c139b6057017f26f68bb99e2e5976f

Tx prefix hash: 969384f0d4cebe6d08735cda35ce337c78cfd81aad9631c3000ec43d8583bc92
Tx public key: 461d2bafeebee42d596c4af7167d6feb14a89e841f847b16c0ad8027df908fa8
Timestamp: 1695145040 Timestamp [UCT]: 2023-09-19 17:37:20 Age [y:d:h:m:s]: 01:226:20:22:50
Block: 851685 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 423228 RingCT/type: yes/0
Extra: 01461d2bafeebee42d596c4af7167d6feb14a89e841f847b16c0ad8027df908fa802110000000533af99f4000000000000000000

1 output(s) for total of 0.924728192000 dcy

stealth address amount amount idx
00: 73fc5d9c7a3bedeb42ac0382dae8e8e77a1afa673dd89057630a670f6c1fed1c 0.924728192000 1305483 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": 851695, "vin": [ { "gen": { "height": 851685 } } ], "vout": [ { "amount": 924728192, "target": { "key": "73fc5d9c7a3bedeb42ac0382dae8e8e77a1afa673dd89057630a670f6c1fed1c" } } ], "extra": [ 1, 70, 29, 43, 175, 238, 190, 228, 45, 89, 108, 74, 247, 22, 125, 111, 235, 20, 168, 158, 132, 31, 132, 123, 22, 192, 173, 128, 39, 223, 144, 143, 168, 2, 17, 0, 0, 0, 5, 51, 175, 153, 244, 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