Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 72084bfb3348094ec824a6a2ef86a238f458b66964570f30a07c479e4b39a618

Tx prefix hash: edff4330c927976eceb3395e5f9238997dba9b628a951f3f4f0b42eeb48edecb
Tx public key: 24976c759d9ec7127c901e9833f30630cd670c9b1437b08cc10c312dbf38606d
Timestamp: 1639049337 Timestamp [UCT]: 2021-12-09 11:28:57 Age [y:d:h:m:s]: 03:031:08:16:07
Block: 391734 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 801360 RingCT/type: yes/0
Extra: 0124976c759d9ec7127c901e9833f30630cd670c9b1437b08cc10c312dbf38606d021100000003e9564d6f000000000000000000

1 output(s) for total of 30.905301329000 dcy

stealth address amount amount idx
00: f9f1b1c422e739d94686f88aec78ec0cb5aeab3dcf375a320fb99304c71ad750 30.905301329000 788277 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": 391744, "vin": [ { "gen": { "height": 391734 } } ], "vout": [ { "amount": 30905301329, "target": { "key": "f9f1b1c422e739d94686f88aec78ec0cb5aeab3dcf375a320fb99304c71ad750" } } ], "extra": [ 1, 36, 151, 108, 117, 157, 158, 199, 18, 124, 144, 30, 152, 51, 243, 6, 48, 205, 103, 12, 155, 20, 55, 176, 140, 193, 12, 49, 45, 191, 56, 96, 109, 2, 17, 0, 0, 0, 3, 233, 86, 77, 111, 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