Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1ebcafae45c648369f496b5a3a5f3176f845d09f1f901c3bc7fbf5e9767e19c6

Tx prefix hash: 4f0088436dde6d75649bee920e9d30f706e09981825996a51151fb3d4fae27dd
Tx public key: 23fed0d5250e6690eb25c8960f474dfdaa1dacc6b1bd32e1f7b9ffcbaece0020
Timestamp: 1727691970 Timestamp [UCT]: 2024-09-30 10:26:10 Age [y:d:h:m:s]: 00:255:00:20:29
Block: 1121329 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 182065 RingCT/type: yes/0
Extra: 0123fed0d5250e6690eb25c8960f474dfdaa1dacc6b1bd32e1f7b9ffcbaece0020021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 49a54104d307d21f05bb047749083c3fecc7b62d2e83a9a0fb35ffad4c91389e 0.600000000000 1603564 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": 1121339, "vin": [ { "gen": { "height": 1121329 } } ], "vout": [ { "amount": 600000000, "target": { "key": "49a54104d307d21f05bb047749083c3fecc7b62d2e83a9a0fb35ffad4c91389e" } } ], "extra": [ 1, 35, 254, 208, 213, 37, 14, 102, 144, 235, 37, 200, 150, 15, 71, 77, 253, 170, 29, 172, 198, 177, 189, 50, 225, 247, 185, 255, 203, 174, 206, 0, 32, 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