Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 324abd73619fa7c8ba5ec2b9a2157c78d0a75638623b5014cb17bf2a9bf87922

Tx prefix hash: 0ec7acef3d7197aa129e82fad0416ab72df414c1c5f88e4aa6b7f5b9645fe1fe
Tx public key: 35b840f83afeb37da718d65f4a5a2dd4a0a7a328c8cabc80d83aeb2b34d66df6
Timestamp: 1726507090 Timestamp [UCT]: 2024-09-16 17:18:10 Age [y:d:h:m:s]: 00:115:20:07:14
Block: 1111501 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 82833 RingCT/type: yes/0
Extra: 0135b840f83afeb37da718d65f4a5a2dd4a0a7a328c8cabc80d83aeb2b34d66df6021100000014e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 29dd93c5fc5f0c8822d16da386c6ada96c31a07f22868b0eb5521d20e60a28eb 0.600000000000 1590484 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": 1111511, "vin": [ { "gen": { "height": 1111501 } } ], "vout": [ { "amount": 600000000, "target": { "key": "29dd93c5fc5f0c8822d16da386c6ada96c31a07f22868b0eb5521d20e60a28eb" } } ], "extra": [ 1, 53, 184, 64, 248, 58, 254, 179, 125, 167, 24, 214, 95, 74, 90, 45, 212, 160, 167, 163, 40, 200, 202, 188, 128, 216, 58, 235, 43, 52, 214, 109, 246, 2, 17, 0, 0, 0, 20, 233, 20, 221, 21, 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