Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bcad61ff2311cdbcbf1cec33f9fb1df3fe5a6548f879153d868389618a539ba8

Tx prefix hash: 54bdbb0ab6f0961f486fcadc16c1b6fe7c2ed96012d5a1d424a50898e6e7a18f
Tx public key: a94613a32014ebba51d3e5b0157afd59984b5151cfc7dfd3e9b5020f28e90356
Timestamp: 1729926435 Timestamp [UCT]: 2024-10-26 07:07:15 Age [y:d:h:m:s]: 00:159:17:11:46
Block: 1139820 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 113946 RingCT/type: yes/0
Extra: 01a94613a32014ebba51d3e5b0157afd59984b5151cfc7dfd3e9b5020f28e903560211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0923d56dcf8dc96026f0ecefa773f18718c9478d56f27c735113c21aefa0be4d 0.600000000000 1623607 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": 1139830, "vin": [ { "gen": { "height": 1139820 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0923d56dcf8dc96026f0ecefa773f18718c9478d56f27c735113c21aefa0be4d" } } ], "extra": [ 1, 169, 70, 19, 163, 32, 20, 235, 186, 81, 211, 229, 176, 21, 122, 253, 89, 152, 75, 81, 81, 207, 199, 223, 211, 233, 181, 2, 15, 40, 233, 3, 86, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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