Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6fb513677e7ca07da16d795a52f2e1c536bb8984101c46e528bd38326fa8ceb5

Tx prefix hash: 0691569edbc3c5c1fe054bc570b30fd2089d756138274e47186f5d538a591611
Tx public key: c29d5f8e2e1190f831c21a037bc55f226a045236fa066574e051e2e61a0f20f7
Timestamp: 1582386320 Timestamp [UCT]: 2020-02-22 15:45:20 Age [y:d:h:m:s]: 04:310:18:13:56
Block: 70286 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1114646 RingCT/type: yes/0
Extra: 01c29d5f8e2e1190f831c21a037bc55f226a045236fa066574e051e2e61a0f20f702110000000103d36d11000000000000000000

1 output(s) for total of 359.016251524000 dcy

stealth address amount amount idx
00: 97f889767b9ed28acde2ab495f56d2d2ea8b44804be7d18a1e0a098f317bf1f3 359.016251524000 129825 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": 70296, "vin": [ { "gen": { "height": 70286 } } ], "vout": [ { "amount": 359016251524, "target": { "key": "97f889767b9ed28acde2ab495f56d2d2ea8b44804be7d18a1e0a098f317bf1f3" } } ], "extra": [ 1, 194, 157, 95, 142, 46, 17, 144, 248, 49, 194, 26, 3, 123, 197, 95, 34, 106, 4, 82, 54, 250, 6, 101, 116, 224, 81, 226, 230, 26, 15, 32, 247, 2, 17, 0, 0, 0, 1, 3, 211, 109, 17, 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