Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d205d6180d9fb424e68642aee9a039aebd34ee384f099b4e601d3bc30fb955df

Tx prefix hash: 36a1486ceb9bb3ae72e953e24732ea49177e5f695b9562b91fb6d5a832c570f8
Tx public key: bad1f88bfde54f65118ca775dea80d1d5403b56e9adfe0f12c869beb794ea1f4
Timestamp: 1702567119 Timestamp [UCT]: 2023-12-14 15:18:39 Age [y:d:h:m:s]: 01:037:01:50:59
Block: 913025 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 287824 RingCT/type: yes/0
Extra: 01bad1f88bfde54f65118ca775dea80d1d5403b56e9adfe0f12c869beb794ea1f402110000000a75e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 12bafba6e2ebcf4db72fc16cb9472cdce419533714f387f836cd5ea6cf9ef0e3 0.600000000000 1370265 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": 913035, "vin": [ { "gen": { "height": 913025 } } ], "vout": [ { "amount": 600000000, "target": { "key": "12bafba6e2ebcf4db72fc16cb9472cdce419533714f387f836cd5ea6cf9ef0e3" } } ], "extra": [ 1, 186, 209, 248, 139, 253, 229, 79, 101, 17, 140, 167, 117, 222, 168, 13, 29, 84, 3, 181, 110, 154, 223, 224, 241, 44, 134, 155, 235, 121, 78, 161, 244, 2, 17, 0, 0, 0, 10, 117, 227, 240, 233, 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