Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d3ecbfec52988113bbdb9193025cf5954e8b6dfaf229c4538524796cbb936377

Tx prefix hash: 5921c1ebcd986374917273a3df8b6f5658e8376928976d90d286915eb0f187a9
Tx public key: 4cb46a2535339926c8be58a2b6a2fd72e61bca4c1c81e8cc804fb50c629cd0ba
Timestamp: 1714590838 Timestamp [UCT]: 2024-05-01 19:13:58 Age [y:d:h:m:s]: 00:319:17:41:37
Block: 1012717 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 228571 RingCT/type: yes/0
Extra: 014cb46a2535339926c8be58a2b6a2fd72e61bca4c1c81e8cc804fb50c629cd0ba0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e6899710f397f4a561aa937b9c5239dbd7ce1c590410ada6b2469f67c05ae006 0.600000000000 1475325 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": 1012727, "vin": [ { "gen": { "height": 1012717 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e6899710f397f4a561aa937b9c5239dbd7ce1c590410ada6b2469f67c05ae006" } } ], "extra": [ 1, 76, 180, 106, 37, 53, 51, 153, 38, 200, 190, 88, 162, 182, 162, 253, 114, 230, 27, 202, 76, 28, 129, 232, 204, 128, 79, 181, 12, 98, 156, 208, 186, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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