Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8b52932e058c278ec86aa09273d4e2af80405becaa1ba1ba8bf99b50ad86b4e0

Tx prefix hash: 0eb81c33447ef5adac8447b1897ee8c0cc22a7c9e79dce0cf22f633920a82726
Tx public key: f233d52fda9687e8ab29dfb9587baa98e755bf3a203d7a3d5155b85e8705ba33
Timestamp: 1723098560 Timestamp [UCT]: 2024-08-08 06:29:20 Age [y:d:h:m:s]: 00:218:09:21:39
Block: 1083240 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 155988 RingCT/type: yes/0
Extra: 01f233d52fda9687e8ab29dfb9587baa98e755bf3a203d7a3d5155b85e8705ba33021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 38c1a64f3072692463da7d3bbe39d70795f1f9844e53f5739c50a9454ab689c5 0.600000000000 1557083 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": 1083250, "vin": [ { "gen": { "height": 1083240 } } ], "vout": [ { "amount": 600000000, "target": { "key": "38c1a64f3072692463da7d3bbe39d70795f1f9844e53f5739c50a9454ab689c5" } } ], "extra": [ 1, 242, 51, 213, 47, 218, 150, 135, 232, 171, 41, 223, 185, 88, 123, 170, 152, 231, 85, 191, 58, 32, 61, 122, 61, 81, 85, 184, 94, 135, 5, 186, 51, 2, 17, 0, 0, 0, 4, 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