Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c51be839d120a48579b3cc1a99dae754111c1ad58806439a1f58ed884a27e37a

Tx prefix hash: 3f38ca1a6527201cd10a1f025d956f9bb23306a1cb20c071241117fea9ebc0a1
Tx public key: 8fe8f144191b5abdf6b01abb8199c35af8073e9aed6ff0ce4b41763811db91a5
Timestamp: 1717463863 Timestamp [UCT]: 2024-06-04 01:17:43 Age [y:d:h:m:s]: 00:306:01:23:04
Block: 1036531 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 218727 RingCT/type: yes/0
Extra: 018fe8f144191b5abdf6b01abb8199c35af8073e9aed6ff0ce4b41763811db91a50211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 603b3c938ada5582212dbf1b5ffcf7b32198a29d6f398f4b81f70d28d667d329 0.600000000000 1505058 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": 1036541, "vin": [ { "gen": { "height": 1036531 } } ], "vout": [ { "amount": 600000000, "target": { "key": "603b3c938ada5582212dbf1b5ffcf7b32198a29d6f398f4b81f70d28d667d329" } } ], "extra": [ 1, 143, 232, 241, 68, 25, 27, 90, 189, 246, 176, 26, 187, 129, 153, 195, 90, 248, 7, 62, 154, 237, 111, 240, 206, 75, 65, 118, 56, 17, 219, 145, 165, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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