Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 14c9c7daae1992d91de703692ed74bc04922ef09d9d7b86cb95f35ff7ee25d9a

Tx prefix hash: 548d273c463dc093078d15cb59bb69a05e1284b35d3d9ab8180c3e8d300fa943
Tx public key: 4d0d9cdaf0931b6a7e986e6fcfb4ca97ad4696c9ea4f0e4f75292952e38ae6da
Timestamp: 1702421871 Timestamp [UCT]: 2023-12-12 22:57:51 Age [y:d:h:m:s]: 01:335:10:53:45
Block: 911844 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 498588 RingCT/type: yes/0
Extra: 014d0d9cdaf0931b6a7e986e6fcfb4ca97ad4696c9ea4f0e4f75292952e38ae6da021100000001e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5c63306ff96e8e036552f6e0f455467543ab39ab3dd4ceaeb21b8f4f4bcbcf9b 0.600000000000 1369060 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": 911854, "vin": [ { "gen": { "height": 911844 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5c63306ff96e8e036552f6e0f455467543ab39ab3dd4ceaeb21b8f4f4bcbcf9b" } } ], "extra": [ 1, 77, 13, 156, 218, 240, 147, 27, 106, 126, 152, 110, 111, 207, 180, 202, 151, 173, 70, 150, 201, 234, 79, 14, 79, 117, 41, 41, 82, 227, 138, 230, 218, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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