Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4c55c7e10fbbc84685ac5f3d671b055f59dfcc10c2e543b8de50d72fc52a9b6e

Tx prefix hash: 632711e4216ca5f2113cdc4653b94d8cba0b0248f0fdf143dc44848be640a2b4
Tx public key: 68cacba51adb0cc280ec31b8e998ce6a03c21342f6e21ea707a6a08f8f103298
Timestamp: 1734190586 Timestamp [UCT]: 2024-12-14 15:36:26 Age [y:d:h:m:s]: 00:341:09:15:04
Block: 1175107 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 241485 RingCT/type: yes/0
Extra: 0168cacba51adb0cc280ec31b8e998ce6a03c21342f6e21ea707a6a08f8f1032980211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1c727876919f8144b6631fd126e1c4ffe0b9bcee0d5815d3db60c3586abc8069 0.600000000000 1661342 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": 1175117, "vin": [ { "gen": { "height": 1175107 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1c727876919f8144b6631fd126e1c4ffe0b9bcee0d5815d3db60c3586abc8069" } } ], "extra": [ 1, 104, 202, 203, 165, 26, 219, 12, 194, 128, 236, 49, 184, 233, 152, 206, 106, 3, 194, 19, 66, 246, 226, 30, 167, 7, 166, 160, 143, 143, 16, 50, 152, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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