Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf85e7448eb5fac57d05f14d257932eaced66b84d0f44fe0ab1bf021b7127820

Tx prefix hash: ac72f460aaf0209d4189c8e15d1e9675e17c7c10a18c58d9850fa99dec43b01d
Tx public key: c685a5f0978e428f8586ae871e0544ad233f0d0b5cae81726b0548a60c9ce4cd
Timestamp: 1645483948 Timestamp [UCT]: 2022-02-21 22:52:28 Age [y:d:h:m:s]: 02:354:02:11:52
Block: 443647 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 772229 RingCT/type: yes/0
Extra: 01c685a5f0978e428f8586ae871e0544ad233f0d0b5cae81726b0548a60c9ce4cd0211000000072e6b1fd5000000000000000000

1 output(s) for total of 20.797618642000 dcy

stealth address amount amount idx
00: b36e2df3bf5eb5c7ff8c492cc691c8e9d213a29e04975b52df4f16a4cc643b16 20.797618642000 856736 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": 443657, "vin": [ { "gen": { "height": 443647 } } ], "vout": [ { "amount": 20797618642, "target": { "key": "b36e2df3bf5eb5c7ff8c492cc691c8e9d213a29e04975b52df4f16a4cc643b16" } } ], "extra": [ 1, 198, 133, 165, 240, 151, 142, 66, 143, 133, 134, 174, 135, 30, 5, 68, 173, 35, 63, 13, 11, 92, 174, 129, 114, 107, 5, 72, 166, 12, 156, 228, 205, 2, 17, 0, 0, 0, 7, 46, 107, 31, 213, 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