Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cfa396e2826f6a1d980b4d2124e080cc0fab02865b1a3fef2aca5039c849da8e

Tx prefix hash: 5de38131a845853bb81755a79e7d52a771940519fc8cdec93597fc8b08ac6f85
Tx public key: 7497dc11d68ea849e8220a6a5adc1c3d6810e9e3e79792e4d4616cff685afe29
Timestamp: 1584916739 Timestamp [UCT]: 2020-03-22 22:38:59 Age [y:d:h:m:s]: 04:297:19:31:24
Block: 86699 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1109933 RingCT/type: yes/0
Extra: 017497dc11d68ea849e8220a6a5adc1c3d6810e9e3e79792e4d4616cff685afe290211000000074ac5aa02000000000000000000

1 output(s) for total of 316.760487488000 dcy

stealth address amount amount idx
00: ce4ffc9ecd4ab0ee7057f114c22166ed18bfd6fe074034bf6e569aafeed400f7 316.760487488000 156469 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": 86709, "vin": [ { "gen": { "height": 86699 } } ], "vout": [ { "amount": 316760487488, "target": { "key": "ce4ffc9ecd4ab0ee7057f114c22166ed18bfd6fe074034bf6e569aafeed400f7" } } ], "extra": [ 1, 116, 151, 220, 17, 214, 142, 168, 73, 232, 34, 10, 106, 90, 220, 28, 61, 104, 16, 233, 227, 231, 151, 146, 228, 212, 97, 108, 255, 104, 90, 254, 41, 2, 17, 0, 0, 0, 7, 74, 197, 170, 2, 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