Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d891fb4c298c896da2b9f812bdeccc91755aa61312a86096234c19cdb78da4df

Tx prefix hash: 3c5d534fc652822a3a43260aadae1b2b730e3a7df97ddf93f30db2554332acb8
Tx public key: 334321092ed401dc03ec4351f8eec197464a2ad6e0e65d7a5072babec4753ae4
Timestamp: 1721770351 Timestamp [UCT]: 2024-07-23 21:32:31 Age [y:d:h:m:s]: 00:252:20:46:39
Block: 1072228 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180639 RingCT/type: yes/0
Extra: 01334321092ed401dc03ec4351f8eec197464a2ad6e0e65d7a5072babec4753ae4021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 45bd405c47f636c567031edfb9cf6dfad23a4099ae3c8e8a7031dedb15f4cc8d 0.600000000000 1544685 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": 1072238, "vin": [ { "gen": { "height": 1072228 } } ], "vout": [ { "amount": 600000000, "target": { "key": "45bd405c47f636c567031edfb9cf6dfad23a4099ae3c8e8a7031dedb15f4cc8d" } } ], "extra": [ 1, 51, 67, 33, 9, 46, 212, 1, 220, 3, 236, 67, 81, 248, 238, 193, 151, 70, 74, 42, 214, 224, 230, 93, 122, 80, 114, 186, 190, 196, 117, 58, 228, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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