Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8f3191891ff90fdf05e58f6f0d3b18c288999df76d234830ad81d95797ca6f84

Tx prefix hash: dce27e521c67ff22972b66cebd695849f335c665472f14697d39532b69fae333
Tx public key: df41838b073c76b9e2029ae24df4a882861241a964849adc01e6e8ee9ea7a90e
Timestamp: 1707060728 Timestamp [UCT]: 2024-02-04 15:32:08 Age [y:d:h:m:s]: 01:019:15:47:01
Block: 950268 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 275067 RingCT/type: yes/0
Extra: 01df41838b073c76b9e2029ae24df4a882861241a964849adc01e6e8ee9ea7a90e02110000000110a1748f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cae4d7f2dd61ba73231994ed3d65e5a95b5dde68dde0978a802407f4bbc7056f 0.600000000000 1408860 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": 950278, "vin": [ { "gen": { "height": 950268 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cae4d7f2dd61ba73231994ed3d65e5a95b5dde68dde0978a802407f4bbc7056f" } } ], "extra": [ 1, 223, 65, 131, 139, 7, 60, 118, 185, 226, 2, 154, 226, 77, 244, 168, 130, 134, 18, 65, 169, 100, 132, 154, 220, 1, 230, 232, 238, 158, 167, 169, 14, 2, 17, 0, 0, 0, 1, 16, 161, 116, 143, 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