Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f4f9ea4c5e583e8ec72fc11bf9a9f1927f5c9d3535953dbcfc7f688e93b2dece

Tx prefix hash: 4660ecc44dc6d0a6bef2a26c3828659adb820d3033a9a2994750d80abfa989d1
Tx public key: bb7cfd885185cccceb59b4cff4c3f96124607706b35a942c20eed5a52d5a880f
Timestamp: 1730306555 Timestamp [UCT]: 2024-10-30 16:42:35 Age [y:d:h:m:s]: 00:025:02:45:24
Block: 1142931 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 17969 RingCT/type: yes/0
Extra: 01bb7cfd885185cccceb59b4cff4c3f96124607706b35a942c20eed5a52d5a880f02110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b67e1418bfec32d5043bf33754ba34f5ffac58087543d2ce3f88b5df8fa20dac 0.600000000000 1626788 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": 1142941, "vin": [ { "gen": { "height": 1142931 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b67e1418bfec32d5043bf33754ba34f5ffac58087543d2ce3f88b5df8fa20dac" } } ], "extra": [ 1, 187, 124, 253, 136, 81, 133, 204, 204, 235, 89, 180, 207, 244, 195, 249, 97, 36, 96, 119, 6, 179, 90, 148, 44, 32, 238, 213, 165, 45, 90, 136, 15, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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