Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c92446f1e7387f88028a6bc6df481a25054c7b3b2ba3f61967eb520ce33fc991

Tx prefix hash: 7c6ac8ed3db2a70ec43b63c8e8f3e37f110eee12354f74f288beb5dc4aa0c107
Tx public key: c013672848131ce0ae73dd77e16e677d6e038711c17c380e6b5ad5c5ec44e4ea
Timestamp: 1707903845 Timestamp [UCT]: 2024-02-14 09:44:05 Age [y:d:h:m:s]: 01:267:07:33:59
Block: 957261 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 449811 RingCT/type: yes/0
Extra: 01c013672848131ce0ae73dd77e16e677d6e038711c17c380e6b5ad5c5ec44e4ea02110000000652d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ef54f341aae49424aeaf5ec87362199614b8c07b62dac484a049b93f803178bf 0.600000000000 1416577 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": 957271, "vin": [ { "gen": { "height": 957261 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ef54f341aae49424aeaf5ec87362199614b8c07b62dac484a049b93f803178bf" } } ], "extra": [ 1, 192, 19, 103, 40, 72, 19, 28, 224, 174, 115, 221, 119, 225, 110, 103, 125, 110, 3, 135, 17, 193, 124, 56, 14, 107, 90, 213, 197, 236, 68, 228, 234, 2, 17, 0, 0, 0, 6, 82, 212, 126, 148, 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