Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4a17a2b0805a366c29fc88bc9211f90488e752d95a5ab65ea534d2a8175ace41

Tx prefix hash: cd19c792b0f4e733912b28aff60b734505b78487f70e05cc5036afd4af8be376
Tx public key: f0b923bb09ecc12ce4ff0754d8e08be49e168c37b8c8ad3cfb8071fbfe8feacf
Timestamp: 1725791536 Timestamp [UCT]: 2024-09-08 10:32:16 Age [y:d:h:m:s]: 00:281:12:16:44
Block: 1105574 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 200972 RingCT/type: yes/0
Extra: 01f0b923bb09ecc12ce4ff0754d8e08be49e168c37b8c8ad3cfb8071fbfe8feacf021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 419e0b23a069cfea0941a49a54092eeef8f94c81139f71e971c20c7da14fda52 0.600000000000 1582949 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": 1105584, "vin": [ { "gen": { "height": 1105574 } } ], "vout": [ { "amount": 600000000, "target": { "key": "419e0b23a069cfea0941a49a54092eeef8f94c81139f71e971c20c7da14fda52" } } ], "extra": [ 1, 240, 185, 35, 187, 9, 236, 193, 44, 228, 255, 7, 84, 216, 224, 139, 228, 158, 22, 140, 55, 184, 200, 173, 60, 251, 128, 113, 251, 254, 143, 234, 207, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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