Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd7591df520dae56e00e128fe324cddc21458830151a53200f175bc45300dc65

Tx prefix hash: 429be088ef523f9c3b0062c7129e303bc1d9896f88e476f46e42179ad50d56a2
Tx public key: 26dc45904c7f58e38d6972b365a18b268b57ceb0043cb4c68bfbd3d5491340bd
Timestamp: 1632788308 Timestamp [UCT]: 2021-09-28 00:18:28 Age [y:d:h:m:s]: 03:130:05:38:15
Block: 342151 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 869575 RingCT/type: yes/0
Extra: 0126dc45904c7f58e38d6972b365a18b268b57ceb0043cb4c68bfbd3d5491340bd02110000000c3fc41461000000000000000000

1 output(s) for total of 45.114083074000 dcy

stealth address amount amount idx
00: cb9512ca4ed5c66c83ec3bfd7de251a748abdf5f349d2f831be69b76e50c0949 45.114083074000 702711 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": 342161, "vin": [ { "gen": { "height": 342151 } } ], "vout": [ { "amount": 45114083074, "target": { "key": "cb9512ca4ed5c66c83ec3bfd7de251a748abdf5f349d2f831be69b76e50c0949" } } ], "extra": [ 1, 38, 220, 69, 144, 76, 127, 88, 227, 141, 105, 114, 179, 101, 161, 139, 38, 139, 87, 206, 176, 4, 60, 180, 198, 139, 251, 211, 213, 73, 19, 64, 189, 2, 17, 0, 0, 0, 12, 63, 196, 20, 97, 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