Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3dec5a603de298f149f3f92839eb0376ad04a4ad14e176771c21a12bd84f0f3f

Tx prefix hash: bbcc6b1ff0af9bd5806635f742faab4c758cb5a9725f98b4495e9cc004b31748
Tx public key: fc45fafefe3156421aec7fcde3bb6b4fe725c6d4b0a6bd9f4266c7af02d61b16
Timestamp: 1705123599 Timestamp [UCT]: 2024-01-13 05:26:39 Age [y:d:h:m:s]: 01:073:08:15:13
Block: 934204 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 313512 RingCT/type: yes/0
Extra: 01fc45fafefe3156421aec7fcde3bb6b4fe725c6d4b0a6bd9f4266c7af02d61b160211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8261192f617d887ece2fc922a0ea9e62fb546349264436f895c7ed13d12e41f7 0.600000000000 1392192 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": 934214, "vin": [ { "gen": { "height": 934204 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8261192f617d887ece2fc922a0ea9e62fb546349264436f895c7ed13d12e41f7" } } ], "extra": [ 1, 252, 69, 250, 254, 254, 49, 86, 66, 26, 236, 127, 205, 227, 187, 107, 79, 231, 37, 198, 212, 176, 166, 189, 159, 66, 102, 199, 175, 2, 214, 27, 22, 2, 17, 0, 0, 0, 2, 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