Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5ca571a3c5ad4fb69f758ff543ae3d5f388b80a7ff69a82600b8f2ffaa6d3bf9

Tx prefix hash: baceb5602829e8130cff050073b9daba36e2b5996c2f08f587bc48d4e457182a
Tx public key: 26f44c8926c80543db4c7a25f07a36b2ee3deb0b6b405e18cac0f0520496b60b
Timestamp: 1725110670 Timestamp [UCT]: 2024-08-31 13:24:30 Age [y:d:h:m:s]: 00:085:00:08:32
Block: 1099921 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 60793 RingCT/type: yes/0
Extra: 0126f44c8926c80543db4c7a25f07a36b2ee3deb0b6b405e18cac0f0520496b60b02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 16758f3b38ec3046e3855ff9083b4672b114002067a1a69a2d495781c3399031 0.600000000000 1575890 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": 1099931, "vin": [ { "gen": { "height": 1099921 } } ], "vout": [ { "amount": 600000000, "target": { "key": "16758f3b38ec3046e3855ff9083b4672b114002067a1a69a2d495781c3399031" } } ], "extra": [ 1, 38, 244, 76, 137, 38, 200, 5, 67, 219, 76, 122, 37, 240, 122, 54, 178, 238, 61, 235, 11, 107, 64, 94, 24, 202, 192, 240, 82, 4, 150, 182, 11, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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