Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3b5a661f9aabc9a8b79bb97639930aab9f9968b7d78cd09781dabfd167f5e1db

Tx prefix hash: 1dee07d6422ac7b26f67a87c2f8f745e5cd9c9eaaa271af014ad2b3a458f4e27
Tx public key: 6c4be05711345f80985971c0d37ceffaa15b10489b49d1e7993223941ecbe538
Timestamp: 1750379256 Timestamp [UCT]: 2025-06-20 00:27:36 Age [y:d:h:m:s]: 00:154:11:31:37
Block: 1308701 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108232 RingCT/type: yes/0
Extra: 016c4be05711345f80985971c0d37ceffaa15b10489b49d1e7993223941ecbe5380211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6d9de40e528457f82bcf7a793f85eb3d9b84a06839f6edc8a78bdc5b8a0ed36d 0.600000000000 1796316 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": 1308711, "vin": [ { "gen": { "height": 1308701 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6d9de40e528457f82bcf7a793f85eb3d9b84a06839f6edc8a78bdc5b8a0ed36d" } } ], "extra": [ 1, 108, 75, 224, 87, 17, 52, 95, 128, 152, 89, 113, 192, 211, 124, 239, 250, 161, 91, 16, 72, 155, 73, 209, 231, 153, 50, 35, 148, 30, 203, 229, 56, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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