Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1ce44e247a4c13cbd66c119fb392a0faf4d28297d3bff2c49f4c172c8b0955ee

Tx prefix hash: bb68290a913947cb17f14ab9ccfe2eb7179a3f791c4bf3a297e4420e85a60e09
Tx public key: a6c45c28af03d1dab8d6f1b73c272d0b1a4f872f5968ac2882d085fa7947be89
Timestamp: 1717794356 Timestamp [UCT]: 2024-06-07 21:05:56 Age [y:d:h:m:s]: 01:161:01:03:35
Block: 1039275 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 373677 RingCT/type: yes/0
Extra: 01a6c45c28af03d1dab8d6f1b73c272d0b1a4f872f5968ac2882d085fa7947be89021100000002d749f511000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 863a88c0e1cccb43774c5059c72e6a098bc8d68ec2351132a2c8f7ad7165a226 0.600000000000 1507908 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": 1039285, "vin": [ { "gen": { "height": 1039275 } } ], "vout": [ { "amount": 600000000, "target": { "key": "863a88c0e1cccb43774c5059c72e6a098bc8d68ec2351132a2c8f7ad7165a226" } } ], "extra": [ 1, 166, 196, 92, 40, 175, 3, 209, 218, 184, 214, 241, 183, 60, 39, 45, 11, 26, 79, 135, 47, 89, 104, 172, 40, 130, 208, 133, 250, 121, 71, 190, 137, 2, 17, 0, 0, 0, 2, 215, 73, 245, 17, 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