Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 301befaf0ee3f32910a4729f8543b8d7b9fb48f60ce86be147e8de9e720cf914

Tx prefix hash: 0003656ef1f051a8a62bddb99fba3d8e042e568edbb0c46b7d7e92ecc2435e33
Tx public key: 3e177aedd588976a81ea9f577b96e569c67a7b03646a4a63bfcf18f63ab41e5c
Timestamp: 1673582996 Timestamp [UCT]: 2023-01-13 04:09:56 Age [y:d:h:m:s]: 02:133:06:47:32
Block: 673604 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 616965 RingCT/type: yes/0
Extra: 013e177aedd588976a81ea9f577b96e569c67a7b03646a4a63bfcf18f63ab41e5c02110000000675e3f0e9000000000000000000

1 output(s) for total of 3.598075513000 dcy

stealth address amount amount idx
00: f483e9640c59b65ddf11d08e850dd92a4d71cfcfc6766ecf91e65270bb45c2c9 3.598075513000 1115219 of 0

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": 673614, "vin": [ { "gen": { "height": 673604 } } ], "vout": [ { "amount": 3598075513, "target": { "key": "f483e9640c59b65ddf11d08e850dd92a4d71cfcfc6766ecf91e65270bb45c2c9" } } ], "extra": [ 1, 62, 23, 122, 237, 213, 136, 151, 106, 129, 234, 159, 87, 123, 150, 229, 105, 198, 122, 123, 3, 100, 106, 74, 99, 191, 207, 24, 246, 58, 180, 30, 92, 2, 17, 0, 0, 0, 6, 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