Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 925d0d3481db2113f1c833da21e0dd1b593c9a02be2cd695e702ab8e133d1f70

Tx prefix hash: 69f8768d326e0da679b18d24662c10b83439cae598459240f676a0a0a7c01b8d
Tx public key: cd70d242ecf81b5315fa4a93255992d36fa3dc3d91cb627648292ffc8f463911
Timestamp: 1674700234 Timestamp [UCT]: 2023-01-26 02:30:34 Age [y:d:h:m:s]: 02:082:01:23:35
Block: 682877 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 580286 RingCT/type: yes/0
Extra: 01cd70d242ecf81b5315fa4a93255992d36fa3dc3d91cb627648292ffc8f4639110211000000015029cbac000000000000000000

1 output(s) for total of 3.352316091000 dcy

stealth address amount amount idx
00: 37dd88b0bf2e59e272c020fd187e91564a2156de4e7f0804403b259d4a7a2e5b 3.352316091000 1125018 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": 682887, "vin": [ { "gen": { "height": 682877 } } ], "vout": [ { "amount": 3352316091, "target": { "key": "37dd88b0bf2e59e272c020fd187e91564a2156de4e7f0804403b259d4a7a2e5b" } } ], "extra": [ 1, 205, 112, 210, 66, 236, 248, 27, 83, 21, 250, 74, 147, 37, 89, 146, 211, 111, 163, 220, 61, 145, 203, 98, 118, 72, 41, 47, 252, 143, 70, 57, 17, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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