Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9a05c8c5b3a01bd1519ed7d6423d8a5206d46f8662156dc3f1e27e860b812321

Tx prefix hash: a491308bf6fd5524eef4f572be9c72b33b3c5e02f7599418da6b1215d42ec9a4
Tx public key: dc3cddb1dd02c8ae0ddd7c4f079924cdc7e63b6e8bd8c5b645717182e846113f
Timestamp: 1702164260 Timestamp [UCT]: 2023-12-09 23:24:20 Age [y:d:h:m:s]: 01:188:18:25:27
Block: 909695 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 395998 RingCT/type: yes/0
Extra: 01dc3cddb1dd02c8ae0ddd7c4f079924cdc7e63b6e8bd8c5b645717182e846113f02110000000375e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bc84fe36a1619d2ff42a4609aa46a80b4485991dcb9cd7375964b21d27bd1c8f 0.600000000000 1366800 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": 909705, "vin": [ { "gen": { "height": 909695 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bc84fe36a1619d2ff42a4609aa46a80b4485991dcb9cd7375964b21d27bd1c8f" } } ], "extra": [ 1, 220, 60, 221, 177, 221, 2, 200, 174, 13, 221, 124, 79, 7, 153, 36, 205, 199, 230, 59, 110, 139, 216, 197, 182, 69, 113, 113, 130, 232, 70, 17, 63, 2, 17, 0, 0, 0, 3, 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