Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f514e5f35a753c5b8af80a11ebfa8123950ca01306f1b6c4c3437009b1f27d7a

Tx prefix hash: c57709f70492646d718f42eb36129cd69153d5e49fa984eb413a8855b166643e
Tx public key: e22f33558e8fc79572d1e2550554d43d1a3fa85ef8e43a62080d084994edea61
Timestamp: 1577832629 Timestamp [UCT]: 2019-12-31 22:50:29 Age [y:d:h:m:s]: 05:002:05:54:21
Block: 36043 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1151595 RingCT/type: yes/0
Extra: 01e22f33558e8fc79572d1e2550554d43d1a3fa85ef8e43a62080d084994edea610211000000774ac5aa02000000000000000000

1 output(s) for total of 466.203395474000 dcy

stealth address amount amount idx
00: 12f3acc3fce5a296486c39e094a540d049f237c1ddcaa3d295e69016b804911c 466.203395474000 60909 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": 36053, "vin": [ { "gen": { "height": 36043 } } ], "vout": [ { "amount": 466203395474, "target": { "key": "12f3acc3fce5a296486c39e094a540d049f237c1ddcaa3d295e69016b804911c" } } ], "extra": [ 1, 226, 47, 51, 85, 142, 143, 199, 149, 114, 209, 226, 85, 5, 84, 212, 61, 26, 63, 168, 94, 248, 228, 58, 98, 8, 13, 8, 73, 148, 237, 234, 97, 2, 17, 0, 0, 0, 119, 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