Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 824a50515a880307a386db83a3ae7ad7417f5282aa56bb0d6d52ddeb9cb9fdb7

Tx prefix hash: f0260591438253f25e241d70906570a621154b3a780d966724b8de325fea0111
Tx public key: 5a005de299180bf408514ce697af8931b329b2b397ab7ca03d7ee0a957835e3e
Timestamp: 1574732839 Timestamp [UCT]: 2019-11-26 01:47:19 Age [y:d:h:m:s]: 05:038:06:09:51
Block: 17574 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1170157 RingCT/type: yes/0
Extra: 015a005de299180bf408514ce697af8931b329b2b397ab7ca03d7ee0a957835e3e021100000001f95225a5000000000000000000

1 output(s) for total of 536.760493373000 dcy

stealth address amount amount idx
00: 681b3b9bc24202c40e0a6843bbd86297d07ebfd43e9dadf8ff55e1c8c84430a3 536.760493373000 25744 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": 17584, "vin": [ { "gen": { "height": 17574 } } ], "vout": [ { "amount": 536760493373, "target": { "key": "681b3b9bc24202c40e0a6843bbd86297d07ebfd43e9dadf8ff55e1c8c84430a3" } } ], "extra": [ 1, 90, 0, 93, 226, 153, 24, 11, 244, 8, 81, 76, 230, 151, 175, 137, 49, 179, 41, 178, 179, 151, 171, 124, 160, 61, 126, 224, 169, 87, 131, 94, 62, 2, 17, 0, 0, 0, 1, 249, 82, 37, 165, 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