Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2316f1782a58743e9f5fa717becfaaf397deaae99196e360d1462f2325803884

Tx prefix hash: b40eea1b4359b267cb899afe184aba690c7f2660b6914cb8ca87a29c73b49c92
Tx public key: b4f914c3142e5959f46def1ddbe95b61d782b44295e48372592a1cbcf033fc88
Timestamp: 1660835920 Timestamp [UCT]: 2022-08-18 15:18:40 Age [y:d:h:m:s]: 02:302:14:35:11
Block: 568608 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 737442 RingCT/type: yes/0
Extra: 01b4f914c3142e5959f46def1ddbe95b61d782b44295e48372592a1cbcf033fc88021100000004ec6d1a1a000000000000000000

1 output(s) for total of 8.016148623000 dcy

stealth address amount amount idx
00: 2b5787d09b41d7e2f4e8013ff1c0d86b03f749266a2ee83378b5548dc7373602 8.016148623000 1001735 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": 568618, "vin": [ { "gen": { "height": 568608 } } ], "vout": [ { "amount": 8016148623, "target": { "key": "2b5787d09b41d7e2f4e8013ff1c0d86b03f749266a2ee83378b5548dc7373602" } } ], "extra": [ 1, 180, 249, 20, 195, 20, 46, 89, 89, 244, 109, 239, 29, 219, 233, 91, 97, 215, 130, 180, 66, 149, 228, 131, 114, 89, 42, 28, 188, 240, 51, 252, 136, 2, 17, 0, 0, 0, 4, 236, 109, 26, 26, 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