Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 02fab86024f42f883db9cbccfae65e4d70c7892d8839639be38148c5750ddfa3

Tx prefix hash: 385840e4a68242164f1c6822683f2c545ef5aa1ebc050fd019914b668b16017a
Tx public key: 0dcc2837b3afcfb910055c4ecb770d81108857e6388a0fadd60f3d9e363992c5
Timestamp: 1735600226 Timestamp [UCT]: 2024-12-30 23:10:26 Age [y:d:h:m:s]: 00:351:12:30:47
Block: 1186755 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 248789 RingCT/type: yes/0
Extra: 010dcc2837b3afcfb910055c4ecb770d81108857e6388a0fadd60f3d9e363992c5021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 59d49ace90f224dbf110bcf6d9d5cfec27a8b99da4a7f0d6f2271094a70af3c5 0.600000000000 1673240 of 15

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": 1186765, "vin": [ { "gen": { "height": 1186755 } } ], "vout": [ { "amount": 600000000, "target": { "key": "59d49ace90f224dbf110bcf6d9d5cfec27a8b99da4a7f0d6f2271094a70af3c5" } } ], "extra": [ 1, 13, 204, 40, 55, 179, 175, 207, 185, 16, 5, 92, 78, 203, 119, 13, 129, 16, 136, 87, 230, 56, 138, 15, 173, 214, 15, 61, 158, 54, 57, 146, 197, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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