Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d2f3b9d1dfc0f4a330b74e91f9b1f358eee882b074b05fe1fa412018c9abe465

Tx prefix hash: fefce24d49ce04638c791fa9effe800b0e432710e9d7b56987b6a797c07ca832
Tx public key: a48c27bfc454ae5d94079325074e3b6608949a13cd6526ed515003eebb073ad5
Timestamp: 1577871718 Timestamp [UCT]: 2020-01-01 09:41:58 Age [y:d:h:m:s]: 05:032:08:06:13
Block: 36256 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1172966 RingCT/type: yes/0
Extra: 01a48c27bfc454ae5d94079325074e3b6608949a13cd6526ed515003eebb073ad5021100000065e39b962a000000000000000000

1 output(s) for total of 465.446398864000 dcy

stealth address amount amount idx
00: 85a6715aa8ec5ad852a09b2227e261250848a29f41b1f98a9c7277e934d8224d 465.446398864000 61371 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": 36266, "vin": [ { "gen": { "height": 36256 } } ], "vout": [ { "amount": 465446398864, "target": { "key": "85a6715aa8ec5ad852a09b2227e261250848a29f41b1f98a9c7277e934d8224d" } } ], "extra": [ 1, 164, 140, 39, 191, 196, 84, 174, 93, 148, 7, 147, 37, 7, 78, 59, 102, 8, 148, 154, 19, 205, 101, 38, 237, 81, 80, 3, 238, 187, 7, 58, 213, 2, 17, 0, 0, 0, 101, 227, 155, 150, 42, 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