Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 53a839c70a1c5367eef640f760bf3e2317f6cad459d11cb0483b5f24a678b95f

Tx prefix hash: 413162feb30c7b735eaa711a25bb3d8097af6ac37076c1cde5790c0b58b45fd0
Tx public key: 6e28512f45c3d189da8b5d8c4495e050ff6ce24668e5f15589f27ed54b8973a6
Timestamp: 1722969913 Timestamp [UCT]: 2024-08-06 18:45:13 Age [y:d:h:m:s]: 00:200:15:21:27
Block: 1082173 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 143256 RingCT/type: yes/0
Extra: 016e28512f45c3d189da8b5d8c4495e050ff6ce24668e5f15589f27ed54b8973a6021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 87d311a236e1dc9271ab2d302377b3dc4d215d919f45edac2a47165981f47b5e 0.600000000000 1555998 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": 1082183, "vin": [ { "gen": { "height": 1082173 } } ], "vout": [ { "amount": 600000000, "target": { "key": "87d311a236e1dc9271ab2d302377b3dc4d215d919f45edac2a47165981f47b5e" } } ], "extra": [ 1, 110, 40, 81, 47, 69, 195, 209, 137, 218, 139, 93, 140, 68, 149, 224, 80, 255, 108, 226, 70, 104, 229, 241, 85, 137, 242, 126, 213, 75, 137, 115, 166, 2, 17, 0, 0, 0, 5, 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