Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 049b86f3704e346f86f206fc73346c154da132c1f326d363297cbf2cd891d89a

Tx prefix hash: 2648228c336f75b0925a9974a2b2b3001e60fa90ca676e32db10951b1c954aa3
Tx public key: 51b0c11961e889c164b67d2e762a07b3cc83d68aa7f7f84044d5e79718a0cfe9
Timestamp: 1736212225 Timestamp [UCT]: 2025-01-07 01:10:25 Age [y:d:h:m:s]: 00:086:07:52:10
Block: 1191822 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 61478 RingCT/type: yes/0
Extra: 0151b0c11961e889c164b67d2e762a07b3cc83d68aa7f7f84044d5e79718a0cfe90211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3e62a937a11a635a7220224bb330d76fa72ee945c5e7d53b090868e137fc7e69 0.600000000000 1678365 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": 1191832, "vin": [ { "gen": { "height": 1191822 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3e62a937a11a635a7220224bb330d76fa72ee945c5e7d53b090868e137fc7e69" } } ], "extra": [ 1, 81, 176, 193, 25, 97, 232, 137, 193, 100, 182, 125, 46, 118, 42, 7, 179, 204, 131, 214, 138, 167, 247, 248, 64, 68, 213, 231, 151, 24, 160, 207, 233, 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